Summary

Issue:

It adds a basic check of every port created in a Helm chart.

• It helps users to verify whether a port is correctly configured.
• In some use cases, when a user adds a port while the Helm chart is not yet deployed, they can specify any service name. Once the Helm chart is deployed, the service name can only be selected from a list discovered dynamically.
• This is especially helpful for Terraform provider users, as they don’t have the console to guide them in choosing the correct service name.

Screenshots / Recordings

Before:

After:
(Without deploying the helm chart)

(After being deployed)

Testing

• Changes tested locally in the relevant Console's pages and Storybooks
• yarn test or yarn test -u (if you need to regenerate snapshots)
• yarn format
• yarn lint

PR Checklist

• I followed naming, styling, and TypeScript rules (see .cursor/rules)
• I performed a self-review (diff inspected, dead code removed)
• I titled the PR using Conventional Commits with a scope when possible (e.g. feat(service): add new Terraform service) - required for semantic-release
• I only kept necessary comments, written in English (watch for useless AI comments)
• I involved a designer to validate UI changes if I am not a designer
• I covered new business logic with tests (unit)
• I confirmed CI is green (Codecov red can be accepted)
• I reviewed and executed locally any AI-assisted code